* Adding your own language to GPSBabelGUI *\r
-------------------------------------------\r
\r
-In first step you need an editor for so called .PO files.\r
-These files contains the strings needed to be translated.\r
-The basic .po file for GPSBabelGUI is default.po and should be\r
-located in your gui directory. The translation can be done with\r
-any editor, but i suggest poedit (http://www.poedit.org/download.php).\r
-poedit is the "must have" tool for dooing such translations.\r
-\r
-If you have done the translation of the billions of message from\r
+In first step you need an editor for .PO files. These files contains the\r
+strings needed to be translated. The basic .po file for GPSBabelGUI is\r
+default.po and should be located in your gui directory. The translation can be\r
+done with any editor, but I suggest poedit (http://www.poedit.org/download.php).\r
+poedit is the "must have" tool for doing such translations.\r
+\r
+If you have done the translation of the billions of messages from\r
the gui have to do the following:\r
\r
- Download and install the package dxgettext from "http://dybdahl.dk/dxgettext"\r
- Create a new folder below your gui directory in form\r
<your-gui-directory>\locale\<LC>\LC_MESSAGES\r
- Replace <LC> with the shortcut for your language.\r
-- The file "languagecodes.txt" from dxgettext is good reference for\r
+- The file "languagecodes.txt" from dxgettext is a good reference for\r
finding the valid shortcut.\r
- (1) Move your new default.po to folder LC_MESSAGE below <your-LC>.\r
- (2) Right-mouse-click on the .po file ... and you should see a new command\r
in your context menu "compile to mo file" ... doit.\r
- Borland Delphi uses a lot of internal strings, but you don't have to\r
- translate them too. On\r
+ translate them. On\r
"http://svn.berlios.de/wsvn/dxgettext/trunk/translations/" you will find\r
a lot of Delphi internal translations. For our gui you should download\r
"delphi.po" for Delphi5 and for <your-LC>\r
\r
- That's all, but please please please, send us a copy of your translation.\r
A mail to gpsbabel-misc@lists.sourceforge.net with your translated\r
- default.po will be immediatly implemented in the project and will be\r
- available for many other users.\r
+ default.po will be implemented in the project (as fast as possible) and\r
+ will be available for many other users.\r
\r
\r
* Getting the source *\r
----------------------\r
\r
There are two ways to get the source of the gui. One of them is source\r
-release package you can download from fourceget. Open "www.gpsbabel.org"\r
+release package you can download from SourceForge. Open "www.gpsbabel.org"\r
in your browser and go over "downloads" to the download list. The file you\r
need is called gpsbabel-<version>-<release>.tar.gz. The gui source you will\r
find in the win32/gui-2 folder.\r
\r
The second way is to checkout the current development tree with CVS.\r
At SourceForge.net you will find the infos for working with cvs.\r
+("http://sourceforge.net/cvs/?group_id=58972" for a short visit)\r
\r
To checkout the gpsbabel source tree the command line should look like this:\r
\r
receive the complete source tree like the source tree but with all\r
changes made after the latest release.\r
\r
+I generally encourage developers to work with the CVS tree instead of\r
+the snapshots.\r
+\r
\r
* Compiling from source *\r
-------------------------\r